Augmenting mobile device operation with intelligent external sensors

ABSTRACT

In embodiments, sensors from an environment in which a mobile device is moving may be used to provide extra input to allow for improved risk analysis and detection in the environment. To prevent unwanted surveillance, proximity to the environment&#39;s sensors may be required. It will be appreciated a coordinator in the environment may assist with handling multiple sensor data provided to the mobile device, and may also assist with identifying risk. The environment may also act as a data feed allowing the mobile device to simply receive additional sensor data and perform its analysis and operation.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a national phase entry under 35 U.S.C. § 371of International Application No. PCT/CN2018/081024, filed Mar. 29, 2018,entitled “AUGMENTING MOBILE DEVICE OPERATION WITH INTELLIGENT EXTERNALSENSORS”, which designated, among the various States, the United Statesof America. The Specifications of the PCT/CN2018/081024 Application ishereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to autonomous and/or semi-autonomousdevice movement, and more particularly, to assisting device movement byincreasing device awareness of potential safety hazards in or enteringits environment and/or proximity.

BACKGROUND AND DESCRIPTION OF RELATED ART

Self-driving cars today rely on radar, LIDAR (Light Detection andRanging), cameras and other sensors installed in a car to detect itsenvironment and possible dangerous situations. The sensors can oftendetect issues/danger more precisely and faster than human eyes.Digitized sensor details may be processed by on board computer(s) toestablish a model of the car's surroundings. A processing environment,such as an Artificial Intelligence tasked with interpreting the sensordetails the car was able to detect and it may then adjust the car'stravel to select the best route forward, and operate the caraccordingly.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings.

FIG. 1 illustrates an exemplary environment 100.

FIG. 2 illustrates an exemplary sequence diagram 200.

FIG. 3 illustrates an exemplary sequence diagram 300.

FIG. 4 illustrates an exemplary intersection environment 400.

FIG. 5 illustrates an exemplary environment illustrating a computerdevice 500, in accordance with various embodiments.

FIG. 6 illustrates an exemplary environment 600 illustrating a storagemedium.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents. Alternate embodiments of the presentdisclosure and their equivalents may be devised without parting from thespirit or scope of the present disclosure. It should be noted that likeelements disclosed below are indicated by like reference numbers in thedrawings.

As noted above a car may detect its environment and an AI may adjustoperation of the car based on what is detected. One limitation of thissystem, however, is that the car is limited to what it can sense. Itwill be appreciated that a car's line of sight may be obscured, such asby other vehicles, buildings, permanent or temporary structures,weather, obstructions on the car (snow, ice, mud,attachments/equipment/stickers added to the car), electromagnetic (EM)or ultrasonic interference, misaligned bumpers, extreme temperatures,unusual lighting, etc. For example, consider the simple example of a carand a bicycle approaching an intersection from different directions. Itis not possible for a LIDAR or a camera to detect the bicycle hiddenfrom view due to being located around the corner of a building. If thebike is traveling from behind the building toward the intersection, thecar may not be able to detect the bike until they are about tounexpectedly meet (crash) in the intersection. Further, it will beappreciated that under some circumstances the car may fail to recognizeobjects in its environment. A well-publicized fatal accident is that ofa Tesla car that failed to slow down when a truck pulled across its pathand the truck's coloration (white-colored) blended in with thebackground environment (similarly-colored sky). Although the exactreason for why the car did not recognize the truck was underinvestigation, these and other such sensory troubles suggest that, ifpossible, assisting the car or other moving device to understand what'sin its environment would represent an important improvement toautonomous and/or semi-autonomous vehicle movement.

For reference, “levels” have been associated with movable devices, suchas cars. Level 0 represents no automation. Level 1 provides some driverassistance, such as adaptive cruise control that may adjust steering orspeed (but not both simultaneously). Level 2 provides partialautomation, such as braking, acceleration, or steering, but the driveris expected to remain in control and respond to traffic, trafficsignals, hazards, etc. Level 3 provides conditional automation, where acar may generally control its movement but a driver is expected to beable to take control at any moment. It will be appreciated that whilethe driver is expected to remain alert, it is likely drivers will not bealert after some time of letting the car be in control. Level 4 provideshigh automation, so that, for example, in restricted or otherwisewell-understood environments (e.g., while on a highway), the car may beentirely self-controlled with no driver involvement. But when on sidestreets the driver would be required to control the car. Level 5represents the current pinnacle of autonomous devices where fullautomation is provided and, for example, a car, may operate on any roadin any conditions a human driver could operate. Errors in the imagedetection or other sensor interpretation mistakes that led to the Teslacrash may cause crashes for any level 3 or higher device.

The following discussion will cover adding other inputs that may beexternal to a mobile device (e.g., car, bus, motorcycle, bike, plane,drone, balloon, or any device that may direct its movement in some way)to assist the device with having a better model from which to makeautomation decisions, e.g., to self-direct its movement or take otheraction. It will be appreciated that while discussion is focusing onmobile devices, the discussion may include devices/mechanisms that maycontrol movement of another device. In one embodiment, existing camerasin the environment are temporarily used to increase the data availableto the mobile device. For example, cameras already installed onroadways, in intersections (e.g., on the traffic lights), on buildings,etc. may be used. It will be appreciated cameras are just one example tohighlight operation of some of the illustrated and/or disclosedembodiments, but it will be appreciated than any other sensor may beused to assist a mobile device. In the context of the car and bikeapproaching an intersection, FIG. 1 discusses using building and/orintersection camera(s) to assist with identifying potential unwantedinteraction between a mobile device such as a car, and the bicycle.

It will be appreciated there are many different techniques that may beemployed for object and other data recognition in input data, such asvisual input data. See for example, Practical object recognition inautonomous driving and beyond; Teichman & Thrun; Advanced Robotics andits Social Impacts (2011) pgs. 35-38 (DOI: 10.1109/ARSO.2011.6301978).Or Object recognition and detection with deep learning for autonomousdriving applications; Uçar, Demir, & Güzelis, (Jun. 2, 2017) accessibleat Internet uniform resource locator (URL)doi.org/10.1177/0037549717709932. Or Towards Fully Autonomous Driving:Systems and Algorithms; Levinson, Askeland, et. al., accessible at URLwww.cs.cmu.edu/˜zkolter/pubs/levinson-iv2011.pdf. Through used of theseand other recognition systems, a mobile device, such as a car, inconjunction with external perspectives provided by the exemplary camerasor other sensors, may cooperatively, either working together, or onedevice providing data to another (e.g., an intersection camera mayprovide data to a car to assist its detecting issues), to assist withmovement of the mobile device.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations do not have to be performedin the order of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments. For the purposes of the present disclosure,the phrase “A and/or B” means (A), (B), or (A and B). For the purposesof the present disclosure, the phrase “A, B, and/or C” means (A), (B),(C), (A and B), (A and C), (B and C), or (A, B and C). The descriptionmay use the phrases “in an embodiment,” or “in embodiments,” which mayeach refer to one or more of the same or different embodiments.Furthermore, the terms “comprising,” “including,” “having,” and thelike, as used with respect to embodiments of the present disclosure, areconsidered synonymous.

As used herein, the term “circuitry” or “circuit” may refer to, be partof, or include an Application Specific Integrated Circuit (ASIC), anelectronic circuit, a processor (shared, dedicated, or group) and/ormemory (shared, dedicated, or group) that execute one or more softwareor firmware programs, a combinational logic circuit, processor,microprocessor, programmable gate array (PGA), field programmable gatearray (FPGA), digital signal processor (DSP) and/or other suitablecomponents that provide the described functionality. Note while thisdisclosure may refer to a processor in the singular, this is forexpository convenience only, and one skilled in the art will appreciatemultiple processors, processors with multiple cores, virtual processors,etc., may be employed to perform the disclosed embodiments.

FIG. 1 illustrates an exemplary environment 100. As illustrated thereare structures 102-106 that may contain sensors 108-112 such as camerasas illustrated, though it will be appreciated they may be these and/orcombination of other types of sensors, such as proximity detectors,motion detectors, short or long range identification systems (e.g., RFIDreaders, facial detectors, object recognizers/detectors, patterndetectors, license plate or other marker/ID readers, magnetic or othersignal recognizers, etc. In the illustrated embodiment, let's assume useof cameras to monitor areas.

In the illustrated embodiment, one or more sensors 108-112 are used toassist with detecting potentially dangerous situations, such as anobstacle that might not be detectable from one perspective but that maybe identifiable through use of other sensors, or other dangeroussituation. It will be appreciated dangerous situations may be caused bysoftware errors of an artificial intelligence (AI) operating a mobiledevice, such as a transportation device such as a car, errors introducedby human drivers, device failure such as flat tires or other mechanicalfailure, or simply a limited field of vision. For example, an autonomous(e.g., level 4 or 5) or semi-autonomous (e.g., level 3) vehicle, such asthe illustrated car 114 is expected to have a variety of sensors 116,118, that are used to identify the car's local environment and providedata required for the device to navigate, e.g., on a road 120. In theillustrated embodiment it will be appreciated that the vehicles sensors116, 118 have a field of view limited by the environment. Asillustrated, buildings 104, 106 are blocking the view of activity of across street 122. If the vehicle 114 is autonomously navigating down theroad 120, and a cyclist 124 is riding down the cross street 122, it ispossible the vehicle and cyclist (or other obstruction that may beundetectable) may unexpectedly meet at the intersection 126 because thevehicle's field of view was obstructed by the buildings 104, 106.

In the illustrated embodiment, other vantage points 108-112, external tothe vehicle, may be used to augment the limited visibility available tothe vehicle. In one embodiment, a recognition system, employing videoanalytic algorithms and domain specific rules, may be used to analyze anenvironment, including identifying types of objects in the vicinity ofthe sensor, object movement, speed, trajectory, scene classification,content analysis, movement prediction, etc., and in the case ofvehicles, domain specific analysis such as lane detection, speeddetection, navigation violations, erratic behavior, etc. and use thisanalysis to identify activity on the streets 120, 122. Based on theanalysis, potentially dangerous situations, such as an imminentpotential collision, may be predicted.

It will be appreciated the recognition system may be embodied in avariety of locations. For example, a smart city might a comprehensivesensor network including cameras, radar, LIDAR, sonar, air qualitydetectors, leak detectors, etc. and it may use these sensors to monitoractivity in the city such as movement of the vehicle 114 and cyclist 124and determine that a collision is likely at the intersection 126 andthis information may be sent to the vehicle so that its autonomousdriving AI may respond to the potential threat, e.g., by breaking,swerving, stopping, etc. and/or this information may be provided to ahuman driver in the vehicle so that the driver may respond. In anotherembodiment, external sensors, such as cameras 108-112 may collectinformation from their environment (e.g., anything within a sensor'sperceptible input area), and apply the recognition system to identifywhat is in the input area and provide this information to a device suchas the vehicle. In this embodiment, the vehicle interprets received datato identify a threat, obstacle, or the like that should be avoided.

In the illustrated embodiment, it will be appreciated that while thevehicle 114 is traveling on street 120, a cyclist 124 on the crossstreet 122 may be rushing toward the intersection 126 and beundetectable by the vehicle's sensors 116, 118. The sensors 110, 112 onthe cross-street 122, however, are able to detect the cyclist. Based onthe apparent trajectories of these two objects, a collision threatassessment may be made and the vehicle appropriately notified of thepotentially dangerous situation. As discussed the determination of thethreat may be made in a recognition system that may be in the vehicle,external to the vehicle such as maintained by the coordinator 130 orother entity, or as a combination of vehicle-based analysis incombination with external input. In one embodiment, external camera108-112 video feeds and associated content analysis are provided to thevehicle for use by the vehicle as if these sensors were part of thevehicle's input systems for it use in performing its navigationoperation.

In one embodiment, in order to protect privacy, a security system isused to prevent an entity from, for example, simply continuouslyreceiving all video feeds and surveilling an environment withoutauthorization to do so. In one embodiment, only vehicles that areproximate to areas of potentially dangerous situations are provided thedata from the sensors 108-112. Thus, for example, since the vehicle 114is approaching the intersection 126, it may have access to the sensors108-112 to assist with threat detection and avoidance. However, becausethe vehicle is not in proximity to a distant sensor 128, data that isbeing generated by this sensor would not be provided to the vehicle. Itwill be appreciated a variety of different techniques may be employed todetermine what data the vehicle is entitled to receive. One suchtechnique is physical proximity, where if a device is nearby it may begranted access to the data. In another embodiment, a device may registerwith a system, such as a smart city, and be provided data relevant, forexample, to a route currently being implemented by the vehicle. Assumingthe location of the vehicle is known, by way of positioning information,e.g., by way of a global positioning system (GPS), or other locationtechnique, then data for areas proximate to the vehicle may be provided.However it will be appreciated, particularly in a known route context,more remote data, or systemic data regarding road trouble, closures,traffic, pedestrians, and the like may be provided to allow the vehicleto optimize its route to avoid as many obstacles as possible.

In another embodiment, sensors may provide their data to devices, suchas the vehicle 114, when the device becomes detectable by a sensor(e.g., visible to a camera), and continue to provide data for as long asthe vehicle is visible (until perhaps a timeout) and for some time afterit leaves the area. In such fashion, sensor 108 may start providing datawhen it detects the vehicle and sensor 112 may provide data since thevehicle is approaching the intersection 126, and sensor 110 may provideits data because it is able to detect beyond the vehicle's restrictedfield of view and assist with identifying potentially dangeroussituations such as a collision between the vehicle and the cyclist 124.Although the security system may be configured to only provide data froma sensor that is able to detect the vehicle, it will be appreciated thatsome sensors, such as sensor 110 may be part of a group defined forexample around the intersection 126 so that data is shared from sensorson both streets 120, 122 with devices that are proximate to theintersection or otherwise receiving data from members of the group.

It will be appreciated detectability depends on the sensor. If thesensor is a camera, detection may mean reading a marking on a device todistinguish one device from another. For example, if the device is avehicle then the marking may be the license plate for the vehicle. Themarker may serve as a lookup ID to allow determining, if using aregistration system, a vehicle is authorized to receive data. If privacyis a concern (and it should be) the security system may be configured touse anonymizers to prevent unwanted tracking of mobile devices such asvehicle 114. If proximity to the sensor (or a sensor in a group) is arequirement for sharing sensor data, other techniques may be used toconfirm proximity. For example, a short-range beacon, such as Bluetooth,Wi-Fi or other limited distance transmitter may be used to associate adevice with a sensor and/or sensor group. Once a device is out of rangeof the sensor beacon then sharing may stop. It will be appreciated thata timeout may be used to allow continued sharing for a time to allow forvehicles that for some reason become undetectable.

Based on the data that a vehicle 114 is able to receive from its sensors116, 118, and from other sensors 108-112, a recognition system (eitherin the vehicle, external to the vehicle, some combination of the two, orother implementation) may detect obstacles or other potentiallydangerous situations and provide or otherwise share an identification ofthe obstacle or potentially dangerous situation with the vehicle. Itwill be appreciated that a communication service may be used tocommunicate with the vehicle, and the service may be point to point,and/or routed through a centralized coordinator, such as a coordinator130, to coordinate data exchanges between sensors and devices, such asvehicle 114. The coordinator may be one or more servers or othermachines that may independently and/or cooperatively operate to maintaina flow of information to devices such as vehicle 114 from varioussensors 108-112, 128.

As discussed above, the coordinator 130 and/or the sensors 108-112, 128may employ analysis to assist with detecting potentially dangeroussituations, such as obstacles in the road or object movement that mightrepresent risk of collision, such as the cyclist 124. It will beappreciated the location of the illustrated coordinator is for exemplarypurposes and the one or more machines represented by the coordinator maybe located elsewhere, and in one embodiment, placement may be made atleast in part based on the communication technology employed. In oneembodiment, the sensors may send messages on a low latency channel, suchas a message service transported over a cellular (e.g., 3G, 5G, etc.)network. As discussed above, sensors may be grouped based on a varietyof characteristics, such as proximity to each other, proximity to animportant location, e.g., an intersection 126, etc. A sensor may be partof multiple groups. Thus, for example, a first group 132 might includeintersection related sensors 108-112, while a second group 134 mightcontain sensors 110, 128 as relating to a section of the cross-street122. As discussed above a security system may restrict access to data,so the vehicle 114 may receive data from any sensor 108-112 in the firstgroup while traveling on the street 120 toward the intersection 126, butonly receive data from all sensors in the second group 110, 128 if thevehicle turns to travel on the cross-street 122 after the intersection.

As noted previously, permission to receive data may be for a limitedtime, requiring a device such as vehicle 114 to reacquire authorizationto receive data. In one embodiment this may be the vehicle beingdetected again by a sensor in the group, or by another authenticationtechnique. It will be appreciated cryptosystems may be employed toencrypt communication between sensors 108-112, 128, the coordinator 130,the vehicle 114, and/or other entities. A public key cryptosystem may beemployed where various entities have public and private keys, and thesekeys may be shared to enable private communication between the variousentities. The sensors may also employ a cryptosystem providing forrolling, changing, expiring, etc. type of keys to enforce the limitedaccess/authentication security requirement. When a device receives a keythat later expires, it will need to contact a sensor 108-112, 128, thecoordinator 130, or other entity managing secured communication of thesensor data. In one embodiment, security credential provisioning mayemploy the Intel® Secure Device Onboard technology (see, e.g., InternetURLwww.intel.com/content/www/us/en/internet-of-things/secure-device-onboard.html),or other such technology.

FIG. 2 illustrates an exemplary sequence diagram 200. Illustrated areexemplary device 202 which may be some type of mobile device, such asthe FIG. 1 vehicle 114; an authorization server 204 which may embody, beembodied in or otherwise communicatively coupled with other machinessuch as FIG. 1 coordinator 130; and a sensor 206 (or sensors), which maybe any device able to detect information about an environment, such asthe FIG. 1 cameras 108-112, 128. As discussed above, various securityand/or cryptographic technologies, contexts, policies, etc. may beemployed to restrict access to data to prevent unwanted and/or illicitsurveillance. In the illustrated embodiment, the mobile device isexpected to be temporarily in an area and therefore it only should begranted temporary access to sensor data.

In one embodiment, in order to join a sensor group such a FIG. 1 group132, the mobile device needs to prove it is proximate to at least onesensor in the group. In the illustrated embodiment, a sensor detects 208the mobile device 202, which for example, could be a camera reading alicense plate and distinctly identifying the device, by a registrationcommunication over a short-range communication technology (showsproximity), or other technique. Once identified the information aboutthe device may be shared 210 with an authorization server 204 or othermachine, which may then temporarily authorize 212 the mobile device. Inone embodiment, the authorization server stores a record of [sensor ID,group ID, mobile device ID], e.g., the ID for a camera that detected avehicle, the sensor group or groups for the camera, and the licenseplate detected on the vehicle.

In one embodiment, the record is stored in a time-based cache, whererecords expire after a predetermined number of minutes after which themobile device will need to re-authenticate to the group. It will beappreciated the length of the timeout may vary on a variety of factors,including the type of vehicle detected, the speed at which it istraveling, traffic, weather, or other conditions affecting theenvironment, etc. An encryption key for the group may be used that has aremaining time to live that is longer than the timeout, so that it wouldallow for a key that changes regularly, for example, daily or weekly,but even with the key the system would ignore communication from thedevice after expiration of the timeout unless the device canre-authenticate with the group to prove physical proximity. In anotherembodiment, sensor data is encrypted with an expiring encryption keythat changes periodically and the mobile device 202 will be able toretrieve a limited number, e.g., one or more, of keys with the temporarycredential; see also operation 218 discussed below. It will beappreciated there are many different cryptosystems, e.g., public keycryptosystems (PKS or PKCS), public key infrastructure (PKI), andprivate cryptographic systems, that may be used to allow the mobiledevice temporary secure access to sensor data. In yet another embodimenta combination of both expiring keys and timeouts may be employed.

In a security system, in addition to or instead of authentication basedon an identifier physically present on the mobile device, such as alicense plate in the case of a vehicle, the mobile device 202 mayauthenticate itself to a group or other environment with data associatedwith the device, which may be an identifier registered and associatedwith the device. It will be appreciated a registry (not illustrated) maybe used to anonymously, or openly, register devices so that they may beknown and more easily authenticated with different groups orenvironments. Even if openly registered, for privacy or otherconsiderations, an authorization server 204 does not need to track/log adevice joining a group when the purpose is to engage in temporary securecommunication with a device passing through an area.

If the mobile device requests 214 to join the group, e.g., with arequest to a sensor 206 and/or authorization server 204, theauthorization server may confirm 216 the mobile device has a validauthorization to access sensor 206 data. For example, the authorizationserver may look in its cache or database for a previously recorded 212temporary authorization. If a previous authorization for the mobiledevice is located, the authorization server may provide 218 temporarycredentials to the mobile device to allow it to access sensor data. Itwill be appreciated that sensor data may be broadcast by the sensoritself, or be routed through another machine such as FIG. 1 coordinator130 to manage communication between the mobile device and provide sensordata.

In one embodiment, if using a key timeout or other authenticationexpiration, a device 202 may receive data, e.g., from a TCP connection,but must periodically revalidate (see, e.g., operations 216, 218) andsend it to the peer of that TCP connection (e.g., a sensor 206), orafter a given timeout a sensor or other peer device will cut off theconnection and ignore communication as discussed above. After credentialrevalidation, communication with a sensor or other cryptographicallysecured device may be reestablished. It will be appreciated thatvalidating authorization to receive data may be separate from encryptingdata shared with the device, and the data may be unencrypted, encryptedover the connection (SSL or TLS) between the device and a sensor(s), orencrypted using a never changing or intermittently changing key, e.g.,weekly, monthly, etc.

In one embodiment, if using an expiring key, a device 202 may use TCP, anetwork broadcasting method, and/or some other technique to receivedata. In this embodiment, devices that may connect to the network toreceive data are not necessarily restricted, however, in this embodimentdata must be encrypted. The encryption may be done by any desiredcryptographic system, such as symmetric cryptography, e.g. AdvancedEncryption Standard (AES). In one embodiment, encryption keys changeregularly, e.g., every few minutes. For example, assume at time Tn, asensor(s) is encrypting data with key Kn. In operation 218 above, thedevice will obtain a “current key” Kn for time Tn and a “next key” Kn+1for time Tn+1 At time Tn+1, if the device it does not re-authenticate byrepeating operation 214, the furthest data the device may decrypt willbe at time Tn+1. When time Tn+2 is reached the device is out of date andcan no longer decrypt messages from a sensor(s) that moved on at timeTn+2 to using the next key Kn+2. If the device desires continued access,it must perform operation 214 again to get access to current keys. Notethat obtaining a current and next key is for convenience in avoidingpotential gaps in time between operations 214, 218. In alternateembodiments, time gaps may be ignored and using 1 key will work.

FIG. 3 illustrates an exemplary sequence diagram 300. In thisembodiment, rather than a sensor(s) 306 looking for mobile device 302,e.g., by looking for license plates or other indicia identifying themobile device, instead an authorization server 304 uses a short rangecommunication technique to broadcast 308 a passcode to the mobiledevice. In one embodiment, the passcode may is an initial code, whichmay be rapidly changing, broadcast to all devices in range to bootstrapconversation with the mobile device. In one embodiment the mobile devicemay use this code to then establish 310 a more secure conversation withthe authorization server. In another embodiment, the authenticationserver broadcasts a One Time Passcode (OTP) to the mobile device, whichthe device may later use to communicate with the authentication serverand/or other devices associated with sensor data to be accessed.

In one embodiment, the authentication server (or a proxy or otherassociated machine) may use a short-range communication technique toensure the mobile device is physically proximate to the authenticationserver 304 and/or the group and/or sensor(s) 306 to which the mobiledevice seeks to obtain sensor data. It will be appreciate there are manytechnologies that may be used for short-range communication, such asUltra high frequency (UHF) broadcasts or other broadcast technologies,e.g., Bluetooth®, ZigBee®, Impulse Radio Ultra Wide Band (IR-UWB),Wi-Fi, EnOcean, Narrow Band Wi-SUN, etc. as well IEEE 802.15.4technologies, such as low-rate wireless personal area networks(LR-WPANs).

In communicating with the authorization server, in one embodiment, amobile device 302 may provide a certificate to validate it is a class ofdevice entitled to receive data, such as sensor(s) 306 data, from theauthorization server 304. It will be appreciated a certificate may beprovided responsive to receiving the broadcast 308 passcode, and/orlater when the mobile device attempts to access sensor data. In oneembodiment, the certificate is in accord with the Intel® EnhancedPrivacy ID (EPID) Security Technology (EPID certificate). (See, forexample, Internet URLsoftware.intel.com/en-us/articles/intel-enhanced-privacy-id-epid-security-technology.)The EPID certificate may previously be issued to the mobile device froman appropriate authority (e.g., a Certificate Authority (CA) root or thelike) and associated with a particular EPID group, such as from an“automobile group”. Having an EPID certificate from an automobile groupwould anonymously authenticate the mobile device to the authorizationserver as a legitimate member of a class of devices with which theauthorization server is willing to provide sensor data. It will beappreciated EPID may be used in lieu of or in combination with otherpublic and/or private key cryptosystems.

If the mobile device requests 312 to join the group, which forillustrative purposes is assumed made to the authorization server, butcould be to a sensor 306 and/or other machine, the authorization servermay confirm 314 the mobile device has valid authorization to accesssensor data. Authorization may be based on the presenting thecredentials initially short-range broadcast 308 to the mobile device,since for the mobile device to have the passcode or other credentialthat was short-range broadcast then the mobile device is known to beproximate to the desired sensor or sensor group and hence presumedauthorized to receive the sensor data. Authorization may also bedetermined based on other information that may have been established 310in subsequent communicating with the authorization server. In requestingto join the group, the mobile device may provide a certificate, such asthe EPID certificate, if not previously presented, to establish themobile device is of a class of devices allowed to receive the type ofdata from the sensor(s) 306.

After confirming 314 the mobile device, the authorization server 304 maysend 316 to the mobile device 302 decryption credentials, such as adecryption key or other information needed to enable the mobile deviceto access sensor data provided by or by way of the sensor(s) 306. In theillustrated embodiment, a sensor shares 318 sensor data with the mobiledevice. However, it will be appreciated the mobile device may receivesensor data directly from a sensor, or by way of another machine such asthe FIG. 1 coordinator 130, the authorization server, or other machine.The mobile device may then decrypt 320 and utilize received sensor data.As discussed with FIG. 1 , for a mobile device that is or is disposedwithin a vehicle, the sensor data may include information to assist withidentifying potentially dangerous situations, upcoming obstacles, etc.and potentially provide early opportunity to avoid trouble. In oneembodiment, the decryption credentials that were sent 316, periodicallyexpire. For example the decryption key for the sensor group may beupdated regularly. If the mobile device still has a need to access thesensor data, it may initiate another join request 312.

FIG. 4 illustrates an exemplary intersection environment 400. Asillustrated there is a vehicle 402 with various sensors, e.g., a camera404 and other sensors (not specifically illustrated) to assist withautonomous or semi-autonomous driving on a road 406. As discussed above,in addition to cameras and other sensors built-in to the vehicle, thevehicle may make use of other sensors such as a camera 408 that may belocated on a traffic signal in intersection, or as part of a photo radarcamera 410 system, or a camera 412 that may be attached to a nearbybuilding and having a view toward the road, or other camera(s) 414 thatmay be in the vicinity and able to be part of a group of cameras andother sensors. The sensors may also include non-visual sensors such as amotion detector 416 that may detect the presence and generalcharacteristics of objects based on signal echo analysis, e.g., ofelectromagnetic, light, and/or sound based emissions, such used inRADAR, sonar, lidar, etc.

In one embodiment, sensors 408-416 analyze their sensor input in real ornear real-time and apply algorithms to detect objects and/or otherinformation revealed by the sensor input. Object detection and/orrecognition, scene detection and/or analysis, motion detection and/oranalysis, geometrical analysis, etc. may be used to identify obstaclesand/or potentially dangerous situations (collectively “risks”) that mayaffect operation of the vehicle 402. As discussed with respect to FIGS.1-3 , some of these risks may be identified by sensors 404 built intothe vehicle. Thus, for example, the vehicle may directly detect ananimal 418 that may have run into the road. But other risks, such asfrom a pedestrian 420, cyclist 422 on the road, or cyclist 424 that maysuddenly cross the road beyond the intersection, these risks areunlikely to be detectable by sensors in the vehicle until the vehicle iscloser to the risk. Given that there is often very limited time torespond to a risk, assistance from the sensors 408-416 external to thevehicle may allow the vehicle extra time and/or opportunity to identifya risk and respond to it.

Therefore, in one embodiment, sensors 408-416 are part of one or moregroups with which the vehicle 402 authenticates as discussed above toreceive sensor data about areas proximate to the vehicle. In oneembodiment, each sensor 408-416 flags input deemed of interest, such asrecognized objects (e.g., recognized animals, people, etc. 418-424). Inthe illustrated embodiment, recognized objects are outlined with abounding box 426-432 (or cube if using 3D data) that is associated witha known scale so that the vehicle's AI or other controlling mechanismmay receive the data and understand the size and relative location of arecognized object. Depending on the sensor the data may also includeinformation about the object such as past motion, current motion, speed,trajectory, etc. Alternatively, a sequence of data from a sensor mayprovide position and size data and the vehicle (or the sensors) maydetermine motion aspects such as speed, direction, and possibility ofcollision through analysis of and comparison between different dataframes. It will be appreciated that all data from sensors may have atimestamp or other associated data (e.g., from a common source, such asglobal positioning system (GPS), network, or other source) to allowsorting inputs at least by time to assist with priority analysis anddata culling if newer data renders other data moot. For example, even ifthe camera 412 can detect the cyclist 422, data from camera 414 may beprioritized over data from camera 412 since camera 414 may be consideredto have better (e.g., more relevant, more precise, etc.) data aboutcyclist 422 due to its better perspective.

In another embodiment, sensors 408-416 may provide their data to aserver or other machine, machine collective, or distributed executionenvironment, such as the FIG. 1 coordinator 130. In this embodiment,rather than (or in addition to) the vehicle 402 receiving sensor datadirectly from the sensors, instead the coordinator or other machine(s)collect sensor data and provide it to the vehicle. In this embodiment,it will be appreciated the coordinator may be able to apply betterdetection algorithms and thus assist the vehicle in identifying and/orresponding to risks. In one embodiment, the coordinator may also usesensor fusion to create virtual sensors out selected ones of the sensorsto provide data not available from any specific sensor. For example,while one sensor may detect a specific object, such as vehicles on theroad, sensor fusion incorporating inputs from cameras, acousticreceivers, etc. may be combined to assess traffic state. The state, ifprovided to a vehicle, may result in the vehicle adjusting itsnavigation to accommodate detected increasing traffic congestion.

In one embodiment, if a sensor 408-416 (or coordinator) detects a movingcyclist 422, it may send sensor data identifying, for example, atimestamp of the detection; the type of object detected, e.g., bicycle;the size of the object, e.g., width and height in a particular unit suchas meters; it's position, which may be determined and provided as anabsolute reference from a predetermined location, as a relativereference with respect to the sensor's position (which will be known ordeterminable), or relative to the position of the mobile device (e.g.,the vehicle 402) requesting the sensor data; speed vector, e.g., speedin a particular unit such as km/h, and heading, where the heading may bedetermined and provided as an absolute reference from the predeterminedlocation, as a relative reference with respect to the sensor's position,or relative to the position of the mobile device; and other data thatthe sensor may provide. That is, if a sensor detects objects with otherobject specific information of interest, it may include that as well.For example, if a camera detects another vehicle, it may provide theabove timestamp, type, size, position and speed information, as well asvehicle specific information such as an identified license plate orother marker identifying the vehicle.

In one embodiment, if a sensor 408-416 (or coordinator) detectsanomalous behavior, such as the signal light 434 being red or otherwiseindicating cyclist 422 should stop for the signal, but it is detectedthe cyclist is not decelerating on approach to the intersection, thesensor may provide the above timestamp, type, size, position and speedinformation, as well as a warning component to indicate the cyclist mayviolate the traffic signal; the warning may allow the vehicle to preparefor the cyclist to perform what would otherwise be an unexpected entryinto the intersection.

In one embodiment, if a sensor 408-416 (or coordinator) detects thetrajectory of two objects are going to collide (where one object may bethe vehicle), the sensor may provide a timestamp, and alert type, e.g.,potential collision, and predicted time of collision, along with thetype, size, position and speed information for each of the objects thatappear to be at risk of colliding. It is assumed that if the two objectsare vehicles, the AI for the two vehicles may, with the alert, slow downor otherwise take evasive action. It will be appreciated that someobjects, such as the cyclists 422, 424 may not have receivers for thesensor data. In one embodiment, a device 436, such as a light and/orsiren, or other warning device, may be used to emit light, noise orother output to alert of an impending problem. For example, a distractedcyclist 422 may see and/or hear the device 436, and become more cautiousand attempt to identify and avoid a potentially dangerous situation.

It will be appreciated a coordinator may receive and process sensor datafrom sensors 408-416 and send data to mobile devices such as the vehicle402. When receiving alerts from sensors and/or the coordinator, thevehicle may perform a variety of autonomous tasks to address and/orrespond to the alert, and it may also notify (e.g., on a heads updisplay or other output) a driver of the alerts to allow the driver todetermine what if any action the driver wishes to take in response tothe alert.

FIG. 5 illustrates an exemplary environment illustrating a computerdevice 500, in accordance with various embodiments. The computer device500 may include any combinations of the components and/or items shownand/or discussed with respect to FIG. 1 sensors 108-112, 128,coordinator 130, or vehicle 114 and associated sensors 116, 118 and/orFIG. 4 sensors 408-416 or vehicle 402 and associated sensor(s) 404. Thecomponents may be implemented as integrated circuits (ICs) or portionsthereof, discrete electronic devices, or other modules, logic, hardware,software, firmware, middleware or a combination thereof adapted in thecomputer device, or as components otherwise incorporated within achassis of a larger system.

The computer device 500 may be an embedded system or any other type ofcomputer device discussed herein. In one example, the computer devicemay be employed in or as a device providing sensors and sensor data asdiscussed herein. In another example, the computer device may be anaggregator in communication with sensors sharing sensed data. Thesensors and aggregators may be separate and dedicated and/orspecial-purpose computer device designed specifically to carry outembodiments discussed herein.

Processor(s) 502 (also referred to as “processor circuitry”) may be oneor more processing elements configured to perform basic arithmetical,logical, and input/output operations by carrying out instructions.Processor circuitry may be implemented as a standalonesystem/device/package or as part of an existing system/device/packageof, for example, in FIG. 1 sensors 108-112, 128, coordinator 130, orvehicle 114 and associated sensors 116, 118 and/or FIG. 4 sensors408-416 or vehicle 402 and associated sensor(s) 404. The processorcircuitry may be one or more microprocessors, one or more single-coreprocessors, one or more multi-core processors, one or more multithreadedprocessors, one or more GPUs, one or more ultra-low voltage processors,one or more embedded processors, one or more DSPs, one or more FPDs(hardware accelerators) such as FPGAs, structured ASICs, programmableSoCs (PSoCs), etc., and/or other processor or processing/controllingcircuit. The processor circuitry may be a part of a system on a chip(SoC) in which the processor circuitry and other components discussedherein are formed into a single IC or a single package. As examples, theprocessor circuitry may include one or more Intel Pentium®, Core®,Xeon®, Atom®, or Core M® processor(s); Advanced Micro Devices (AMD)Accelerated Processing Units (APUs), Epyc®, or Ryzen® processors; AppleInc. A series, S series, W series, etc. processor(s); QualcommSnapdragon® processor(s); Samsung Exynos® processor(s); and/or the like.

In embodiments, the processor circuitry 502 may include a sensor hub(not illustrated), which may act as a coprocessor by processing dataobtained from the sensors 520. The sensor hub may include circuitryconfigured to integrate data obtained from each of the sensors byperforming arithmetical, logical, and input/output operations. Inembodiments, the sensor hub may capable of timestamping obtained sensordata, providing sensor data to the processor circuitry in response to aquery for such data, buffering sensor data, continuously streamingsensor data to the processor circuitry including independent streams foreach sensor, reporting sensor data based upon predefined thresholds orconditions/triggers, and/or other like data processing functions.

Memory 504 (also referred to as “memory circuitry” or the like) may becircuitry configured to store data or logic for operating the computerdevice 500. Memory circuitry may include number of memory devices may beused to provide for a given amount of system memory. As examples, thememory circuitry can be any suitable type, number and/or combination ofvolatile memory devices (e.g., random access memory (RAM), dynamic RAM(DRAM), static RAM (SAM), etc.) and/or non-volatile memory devices(e.g., read-only memory (ROM), erasable programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),flash memory, antifuses, etc.) that may be configured in any suitableimplementation as are known. In one embodiment, memory, such as flashmemory or other memory is or may include a memory device that is a blockaddressable memory device, such as those based on NAND or NORtechnologies. A memory device may also include future generationnonvolatile devices, such as a three dimensional crosspoint memorydevice, or other byte addressable write-in-place nonvolatile memorydevices. In one embodiment, the memory device may be or may includememory devices that use chalcogenide glass, multi-threshold level NANDflash memory, NOR flash memory, single or multi-level Phase ChangeMemory (PCM), a resistive memory, nanowire memory, ferroelectrictransistor random access memory (FeTRAM), anti-ferroelectric memory,magnetoresistive random access memory (MRAM) memory that incorporatesmemristor technology, resistive memory including the metal oxide base,the oxygen vacancy base and the conductive bridge Random Access Memory(CB-RAM), or spin transfer torque (STT)-MRAM, a spintronic magneticjunction memory based device, a magnetic tunneling junction (MTJ) baseddevice, a DW (Domain Wall) and SOT (Spin Orbit Transfer) based device, athyristor based memory device, or a combination of any of the above, orother memory. The memory device may refer to the die itself and/or to apackaged memory product. In various implementations, individual memorydevices may be formed of any number of different package types, such assingle die package (SDP), dual die package (DDP) or quad die package(Q17P), dual inline memory modules (DIMMs) such as microDlMMs orMiniDIMMs, and/or any other like memory devices. To provide forpersistent storage of information such as data, applications, operatingsystems and so forth, the memory circuitry may include one or moremass-storage devices, such as a solid state disk drive (SSDD); flashmemory cards, such as SD cards, microSD cards, xD picture cards, and thelike, and USB flash drives; on-die memory or registers associated withthe processor circuitry 502 (for example, in low power implementations);a micro hard disk drive (HDD); three dimensional cross-point (3D XPOINT)memories from Intel® and Micron®, etc.

Where FPDs are used, the processor circuitry 502 and memory circuitry504 (and/or device storage circuitry 508) may comprise logic blocks orlogic fabric, memory cells, input/output (I/O) blocks, and otherinterconnected resources that may be programmed to perform variousfunctions of the example embodiments discussed herein. The memory cellsmay be used to store data in lookup-tables (LUTs) that are used by theprocessor circuitry to implement various logic functions. The memorycells may include any combination of various levels of memory/storageincluding, but not limited to, EPROM, EEPROM, flash memory, SRAM,anti-fuses, etc.

Data storage circuitry 508 (also referred to as “storage circuitry” orthe like), with shared or respective controllers, may provide forpersistent storage of information such as modules 510, operatingsystems, etc. The storage circuitry may be implemented as solid statedrives (SSDs); solid state disk drive (SSDD); serial AT attachment(SATA) storage devices (e.g., SATA SSDs); flash drives; flash memorycards, such as SD cards, microSD cards, xD picture cards, and the like,and USB flash drives; three-dimensional cross-point (3D Xpoint) memorydevices; on-die memory or registers associated with the processorcircuitry 502; hard disk drives (HDDs); micro HDDs; resistance changememories; phase change memories; holographic memories; or chemicalmemories; among others. As shown, the storage circuitry is included inthe computer device 500; however, in other embodiments, storagecircuitry may be implemented as one or more separate devices that aremounted in, for example, an aggregator 116 separate from the otherelements of the computer device.

In some embodiments, the storage circuitry 508 may include an operatingsystem (OS) (not shown), which may be a general purpose operating systemor an operating system specifically written for and tailored to thecomputer device 500. The OS may include one or more drivers, libraries,and/or application programming interfaces (APIs), which provide programcode and/or software components for modules 510 and/or control systemconfigurations to control and/or obtain/process data from one or moresensors 520 and/or EMCs 522. The modules 510 may be softwaremodules/components used to perform various functions of the computerdevice and/or to carry out functions of the example embodimentsdiscussed herein. In embodiments where the processor circuitry 502 andmemory circuitry 504 includes hardware accelerators (e.g., FPGA cells)as well as processor cores, the hardware accelerators (e.g., the FPGAcells) may be pre-configured (e.g., with appropriate bit streams, logicblocks/fabric, etc.) with the logic to perform some functions of theembodiments herein (in lieu of employment of programming instructions tobe executed by the processor core(s)). For example, the modules maycomprise logic for the corresponding entities discussed with regard toFIG. 1 .

The components of computer device 500 and/or FIG. 1 sensors 108-112,128, coordinator 130, or vehicle 114 and associated sensors 116, 118and/or FIG. 4 sensors 408-416 or vehicle 402 and associated sensor(s)404 may communicate internally or as the case may be, with one another,over the bus 506. The bus may include any number of technologies, suchas a Local Interconnect Network (LIN); industry standard architecture(ISA); extended ISA (EISA); PCI; PCI extended (PCIx); PCIe; anInter-Integrated Circuit (I2C) bus; a Parallel Small Computer SystemInterface (SPI) bus; Common Application Programming Interface (CAPI);point to point interfaces; a power bus; a proprietary bus, for example,Intel® Ultra Path Interface (UPI), Intel® Accelerator Link (IAL), orsome other proprietary bus used in a SoC based interface; or any numberof other technologies. In some embodiments, bus 506 may be a controllerarea network (CAN) bus system, a Time-Trigger Protocol (TTP) system, ora FlexRay system, which may allow various devices (e.g., sensors 520,EMCs 522, etc.) to communicate with one another using messages orframes. Communications circuitry 514 may include circuitry forcommunicating with a wireless network or wired network. For example, thecommunication circuitry may include transceiver (Tx) 216 and networkinterface controller (NIC) 212, and may include one or more processors(e.g., baseband processors, modems, etc.) dedicated to a particularwireless communication protocol.

NIC 212 may be included to provide a wired communication link to anetwork 550, e.g., the cloud, and/or other devices. Wired communicationmay provide an Ethernet connection, an Ethernet-over-USB, and/or thelike, or may be based on other types of networks, such as DeviceNet,ControlNet, Data Highway+, PROFIBUS, or PROFINET, among many others. Anadditional NIC may be included to allow connection with a second network(not shown) or other devices, for example, a first NIC 512 providingcommunications to the network 550 over Ethernet, and a second MCproviding communications to other devices over another type of network,such as a personal area network (PAN) including a personal computer (PC)device. In some embodiments, the various illustrated components, such assensors 520, EMCs 522, PGUs 530, etc. may be connected to the system 500via the NIC 512 as discussed above rather than via the I/O circuitry518.

The Tx 516 may include one or more radios to wirelessly communicate withthe network 550 and/or other devices. The Tx may include hardwaredevices that enable communication with wired networks and/or otherdevices using modulated electromagnetic radiation through a solid ornon-solid medium. Such hardware devices may include switches, filters,amplifiers, antenna elements, and the like to facilitate thecommunications over the air (OTA) by generating or otherwise producingradio waves to transmit data to one or more other devices, andconverting received signals into usable information, such as digitaldata, which may be provided to one or more other components of computerdevice 500. In some embodiments, the various components of theillustrated embodiment, such as sensors 520, EMCs 522, PGUs 530, etc.may be connected to the system 500 via the Tx as discussed above ratherthan via the I/O circuitry 518. In one example, one or more sensors 520may be coupled with system 500 via a short range communication protocol,such as those discussed previously, e.g., BLE or the like. In anotherexample, the PGUs may be coupled with the system via a wirelessconnection (e.g., via Tx 516 or the like) and operate in conjunctionwith one or more remote display protocols, such as the wireless gigabitalliance (WiGiG) protocol, the remote desktop protocol (RDP), PC-over-IP(PCoIP) protocol, the high-definition experience (HDX) protocol, and/orother like remote display protocols.

The Tx 516 may include one or multiple radios that are compatible withany number of 3GPP (Third Generation Partnership Project)specifications, notably Long Term Evolution (LTE), Long TermEvolution-Advanced (LTE-A), Long Term Evolution-Advanced Pro (LTE-APro), and Fifth Generation (5G) New Radio (NR). It can be noted thatradios compatible with any number of other fixed, mobile, or satellitecommunication technologies and standards may be selected. These mayinclude, for example, any Cellular Wide Area radio communicationtechnology, which may include e.g. a 5G communication systems, a GlobalSystem for Mobile Communications (GSM) radio communication technology, aGeneral Packet Radio Service (GPRS) radio communication technology, oran Enhanced Data Rates for GSM Evolution (EDGE) radio communicationtechnology. Other Third Generation Partnership Project (3GPP) radiocommunication technology that may be used includes UMTS (UniversalMobile Telecommunications System), FOMA (Freedom of Multimedia Access),3GPP LTE (Long Term Evolution), 3GPP LTE Advanced (Long Term EvolutionAdvanced), 3GPP LTE Advanced Pro (Long Term Evolution Advanced Pro)),CDMA2000 (Code division multiple access 2000), CDPD (Cellular DigitalPacket Data), Mobitex, 3G (Third Generation), CSD (Circuit SwitchedData), HSCSD (High-Speed Circuit-Switched Data), UMTS (3G) (UniversalMobile Telecommunications System (Third Generation)), W-CDMA (UMTS)(Wideband Code Division Multiple Access (Universal MobileTelecommunications System)), HSPA (High Speed Packet Access), HSDPA(High-Speed Downlink Packet Access), HSUPA (High-Speed Uplink PacketAccess), HSPA+(High Speed Packet Access Plus), UMTS-TDD (UniversalMobile Telecommunications System-Time-Division Duplex), TD-CDMA (TimeDivision-Code Division Multiple Access), TD-SCDMA (TimeDivision-Synchronous Code Division Multiple Access), 3GPP Rel. 8(Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4thGeneration)), 3GPP Rel. 9 (3rd Generation Partnership Project Release9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10), 3GPPRel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12(3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rdGeneration Partnership Project Release 13), 3GPP Rel. 14 (3rd GenerationPartnership Project Release 14), 3GPP LTE Extra, LTE Licensed-AssistedAccess (LAA), UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTSTerrestrial Radio Access), LTE Advanced (4G) (Long Term EvolutionAdvanced (4th Generation)), cdmaOne (2G), CDMA2000 (3G) (Code divisionmultiple access 2000 (Third generation)), EV-DO (Evolution-DataOptimized or Evolution-Data Only), AMPS (1G) (Advanced Mobile PhoneSystem (1st Generation)), TACS/ETACS (Total Access CommunicationSystem/Extended Total Access Communication System), D-AMPS (2G) (DigitalAMPS (2nd Generation)), PTT (Push-to-talk), MTS (Mobile TelephoneSystem), IMTS (Improved Mobile Telephone System), AMTS (Advanced MobileTelephone System), OLT (Norwegian for Offentlig Landmobil Telefoni,Public Land Mobile Telephony), MTD (Swedish abbreviation forMobiltelefonisystem D, or Mobile telephony system D), Autotel/PALM(Public Automated Land Mobile), ARP (Finnish for Autoradiopuhelin, “carradio phone”), NMT (Nordic Mobile Telephony), Hicap (High capacityversion of NTT (Nippon Telegraph and Telephone)), CDPD (Cellular DigitalPacket Data), Mobitex, DataTAC, iDEN (Integrated Digital EnhancedNetwork), PDC (Personal Digital Cellular), CSD (Circuit Switched Data),PHS (Personal Handy-phone System), WiDEN (Wideband Integrated DigitalEnhanced Network), iBurst, Unlicensed Mobile Access (UMA, also referredto as also referred to as 3GPP Generic Access Network, or GANstandard)), Wireless Gigabit Alliance (WiGig) standard, =Wave standardsin general (wireless systems operating at 10-90 GHz and above such asWiGig, IEEE 802.11ad, IEEE 802.11ay, and the like. In addition to thestandards listed above, any number of satellite uplink technologies maybe used for the uplink transceiver, including, for example, radioscompliant with standards issued by the ITU (InternationalTelecommunication Union), or the ETSI (European TelecommunicationsStandards Institute), among others.

Communication circuitry 514 may implement or support any number ofstandards, protocols, and/or technologies datacenters typically use,such as networking technology providing high-speed low latencycommunication. For example, the communication chip(s) may support RoCE(Remote Direct Memory Access (RDMA) over Converged Ethernet), e.g.,version 1 or 2, which is a routable protocol having efficient datatransfers across a network, and is discussed for example at Internet URLRDMAconsortium.com. The chip(s) may support Fibre Channel over Ethernet(FCoE), iWARP, or other high-speed communication technology, see forexample the OpenFabrics Enterprise Distribution (OFED™) documentationavailable at Internet URL OpenFabrics.org. It will be appreciateddatacenter environments benefit from highly efficient networks, storageconnectivity and scalability, e.g., Storage Area Networks (SANs),parallel computing using RDMA, Internet Wide Area Remote Protocol(iWARP), InfiniBand Architecture (IBA), and other such technology. Theexamples provided herein are thus understood as being applicable tovarious other communication technologies, both existing and not yetformulated. Implementations, components, and details of theaforementioned protocols may be those known in the art and are omittedherein for the sake of brevity.

The input/output (I/O) interface 518 may include circuitry, such as anexternal expansion bus (e.g., Universal Serial Bus (USB), FireWire,Thunderbolt, PCI/PCIe/PCIx, etc.), used to connect computer device 500with external components/devices, such as sensors 520, EMCs 522, PGUs530, etc. I/O interface circuitry 518 may include any suitable interfacecontrollers and connectors to interconnect one or more of the processorcircuitry 502, memory circuitry 504, data storage circuitry 508,communication circuitry 514, and the other components of computer device500. The interface controllers may include, but are not limited to,memory controllers, storage controllers (e.g., redundant array ofindependent disk (RAID) controllers, baseboard management controllers(BMCs), input/output controllers, host controllers, etc. The connectorsmay include, for example, busses (e.g., bus 506), ports, slots, jumpers,interconnect modules, receptacles, modular connectors, etc. The I/Ocircuitry 518 may couple the system 500 with sensors 520, EMCs 522, PGUs530, etc. via a wired connection, such as using USB, FireWire,Thunderbolt, RCA, a video graphics array (VGA), a digital visualinterface (DVI) and/or mini-DVI, a high-definition multimedia interface(HDMI), an S-Video, and/or the like. Although FIG. 5 shows that thesensors 520, EMCs 522, and PGUs 530 are coupled with the computer device500 via interface circuitry 518, in other embodiments, the sensors, EMCs522, and PGUs may be communicatively coupled with the computer devicevia Tx 516, using short-range radio links, WiFi signaling, or the like.

Sensors 520 may operate as discussed above with respect to FIGS. 1 and 4sensors 108-112, 116, 118, 128, 404, 408-416 and be any deviceconfigured to detect events or environmental changes, convert thedetected events into electrical signals and/or digital data, andtransmit/send the signals/data to the computer device 500 and/or one ormore EMCs 522. Some of the sensors 520 may be sensors used for providingcomputer-generated sensory inputs in an environment which may includecomputer device 500. Some of the sensors may be sensors used for motionand/or object detection. Examples of such sensors may include, interalia, charged-coupled devices (CCD), Complementarymetal-oxide-semiconductor (CMOS) active pixel sensors (APS), lens-lessimage capture devices/cameras, thermographic (infrared) cameras, LightImaging Detection And Ranging (LIDAR) systems, and/or the like. In someimplementations, the sensors may include a lens-less image capturemechanism comprising an array of aperture elements, wherein lightpassing through the array of aperture elements define the pixels of animage. In embodiments, the motion detection sensors may be coupled withor associated with light generating devices, for example, one or moreinfrared projectors to project a grid of infrared light onto a scene orenvironment, where an infrared camera may record reflected infraredlight to compute depth information.

Some of the sensors 520 may be used for position and/or orientationdetection, ambient/environmental condition detection, and the like.Examples of such sensors may include, inter alia, microelectromechanicalsystems (MEMS) with piezoelectric, piezoresistive and/or capacitivecomponents, which may be used to determine environmental conditions orlocation information related to the computer device 500. In embodiments,the MEMS may include 3-axis accelerometers, 3-axis gyroscopes, and/ormagnetometers. In some embodiments, the sensors may also include one ormore gravimeters, altimeters, barometers, proximity sensors (e.g.,infrared radiation detector(s) and the like), depth sensors, ambientlight sensors, thermal sensors (thermometers), ultrasonic transceivers,and/or the like.

The EMCs 522 may be devices that allow computer device 500 to change astate, position, orientation, move, and/or control a mechanism orsystem. The EMCs may include one or more switches; haptic outputdevices, such as actuators and/or motors (e.g., eccentric rotating mass(ERM) actuators, linear resonant actuator (LRA), piezoelectricactuators, servomechanisms, rotary motors, linear motors, and stepmotors, etc.), thrusters, projectile ejecting devices (e.g., usingspring loaded or compressed air/fluid), and/or the like. In embodiments,the EMCs may comprise speakers, a digital rendering module(s) (e.g., aphysical object with a digital rendering module therein), and/or anotherway to control an acoustic energy emission, an electromagnetic radiationemission, an electric energy application, a magnetic field, and anacceleration or deceleration emitted or experienced by a physicalobject. In embodiments, computer device may be configured to operate oneor more EMCs by transmitting/sending instructions or control signals tothe EMCs based on detected user interactions or other like events.

Picture generation units (PGUs) 530 may generate light (e.g., based ondigital images), which may be directed and/or redirected to opticalelements (OEs) 532, e.g., to a display surface. The digital images maybe any type of content stored by the storage circuitry 508, streamedfrom remote devices via the communication circuitry 514, and/or based onoutputs from various sensors 520, EMCs 522, and/or other objects, or, asdiscussed in FIG. 4 , with respect to the alerting device 436. The OEthat combines the generated light with the external light may bereferred to as a “combiner element”. The PGUs 530 may be one or moreelectronic devices that create or generate digital images to be directedto OEs 532. The combiner element (as well as other OEs) may be a displaysurface, which may be fully or partially opaque or transparent, thatmixes the digital images output by the projector/PGUs 530 with viewedreal-world objects to facilitate augmented reality. In embodiments, theOEs 532 may be a holographic OE, and in some embodiments, the combinerelement may be a hologram or holographic image (e.g., transmissive,reflective, etc.).

The battery 528 may power the computer device 500. In embodiments, thebattery may be a lithium ion battery, a metal-air battery, such as azinc-air battery, an aluminum-air battery, a lithium-air battery, alithium polymer battery, and the like. The battery monitor 526 may beincluded in the computer device 500 to track/monitor various parametersof the battery, such as a state of charge (SoCh) of the battery, stateof health (SoH), and the state of function (SoF) of the battery. Thebattery monitor may include a battery monitoring IC, which maycommunicate battery information to the processor circuitry 502 over thebus 506. The bus may allow components of computer device 500 tocommunicate with one another. The bus may include any number oftechnologies, such as a Local Interconnect Network (LIN); industrystandard architecture (ISA); extended ISA (EISA); Peripheral ComponentInterconnect Express (PCI); PCI extended (PCIx); PCI express (PCIe); anInter-Integrated Circuit (I2C) bus; a Parallel Small Computer SystemInterface (SPI) bus; point to point interfaces; a power bus; aproprietary bus, for example, used in a SoC based interface; or anynumber of other technologies. Suitable implementations and generalfunctionality of such bus systems are known, and are readily implementedby persons having ordinary skill in the art.

While not shown, various other devices may be present within, orconnected to, the computer device 500. For example, I/O devices, such asa display, a touchscreen, or keypad may be connected to the computerdevice 500 via bus 506 to accept input and display outputs. In anotherexample, the computer device may include or be coupled with positioningcircuitry configured to determine coordinates based on signals receivedfrom global navigation satellite system (GNSS) constellations, e.g., toderive GPS data. In another example, the communications circuitry 514may include a Universal Integrated Circuit Card (UICC), embedded UICC(eUICC), and/or other elements/components that may be used tocommunicate over one or more wireless networks.

FIG. 6 illustrates an exemplary environment 600 illustrating a storagemedium that may be transitory, non-transitory or a combination oftransitory and non-transitory media, and the medium may be suitable foruse to store instructions that cause an apparatus, machine or otherdevice, in response to execution of the instructions, to practiceselected aspects of the present disclosure. As will be appreciated byone skilled in the art, the present disclosure may be embodied asmethods or computer program products. Accordingly, the presentdisclosure, in addition to being embodied in hardware as earlierdescribed, may take the form of an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects. Furthermore, thepresent disclosure may take the form of a computer program productembodied in any tangible or non-transitory medium of expression havingcomputer-usable program code embodied in the medium.

In one embodiment, the storage medium is a non-transitory, machinereadable (or machine accessible) medium (NTMRM) 602 including associatedinformation 604 that includes at least instructions 606 to direct one ormore processor 608 to perform various functions delineated by theembodiments discussed herein. In embodiments, the non-transitory,machine readable medium 602 may be implemented in FIG. 1 sensors108-112, 128, coordinator 130, or vehicle 114 and associated sensors116, 118 and/or FIG. 4 sensors 408-416 or vehicle 402 and associatedsensor(s) 404. The processor may access the non-transitory, machinereadable medium 602 over a bus 610. The processor and bus may be thesame or similar as described with respect to the processor 502 and bus506 of FIG. 5 . The non-transitory, machine readable medium may includedevices described for the mass storage 508 of FIG. 5 or may includeoptical disks, thumb drives, or any number of other hardware devices orenvironments providing access to information. In some embodiments, themachine readable medium may be transitory, e.g., signals. In oneembodiment the machine readable medium is non-transitory, then moved toa transitory state, which may then be moved back to a non-transitorystate.

The NTMRM 602 may include code to direct the processor 608 to obtaindata from any of FIGS. 1, 2, 4 sensors 108-112, 116, 118, 128, 220, 404,408-416. The sensor data may be representative of a physicalenvironment. In one embodiment, a modeling engine may direct theprocessor 608 to generate a model of the physical environment based atleast in part on the sensor data. It will be appreciated the model neednot be a visual-based model, and may just be various sensor inputassociated with positional data in any known spatial location system,e.g., longitude/latitude/altitude, 3-point (e.g., XYZ) positions, GPS(Global Positioning System) coordinates, triangulation based oncommunication towers, association with devices having a known location(e.g., printers, routers and other devices may have a known locationthat may be imputed to a device passing in range of it), etc. The modelmay be a suitable collection of data points in the multi-dimensionalspace connected by various geometric shapes or entities and may includetextual and/or contextual information for various surfaces and/orlocations within the environment. The model may be generated using anysuitable modeling techniques/technologies.

The NTMRM may include code to receive and process user input and/or dataassociated with an analysis engine to direct the processor to performsome action, such as obtain data from any of FIGS. 1, 2, 4 sensors108-112, 116, 118, 128, 220, 404, 408-416, interpret user interactionssuch as gestures and/or speech and/or other motion/movement, interactwith other hardware, etc. In some embodiments, sensor and/or other dataprocessed by the processor may include sensor data obtained fromwearable technology which may be used to augment or supplement sensordata. In some embodiments, the NTMRM may include code to direct anaggregator to receive and evaluate sensor data and to instantiatevirtual sensors and/or derive new virtual sensors based on receivedsensor data, and to recognize and respond to emergency situations.

The NTMRM may include code of a semantic engine (not illustrated) todirect the processor 602 to determine one or more semantic attributes,which may be used to influence operation of devices executing the code.The semantic engine may determine aspects such as user activity, userattributes, semantic location, social circumstances, ambient orenvironmental conditions, presence of electronic devices, schedules,communication, etc. that may allow determining what are desirableactions in a given circumstance. User activity semantics may include anyinformation related to user, such as body (or body part) positions ororientations. User attributes may include any information related touser or user preferences.

It will be appreciated any combination of machine readable medium may beutilized, including, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, device, or propagation medium. More specific examples (anon-exhaustive list) of the machine readable medium would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), an optical storage device, a transmission media such asthose supporting the Internet or an intranet, or a magnetic storagedevice. Note that the computer-usable or machine readable medium couldeven be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory. In the context of this disclosure,a computer-usable or machine readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice. The machine readable medium may include a propagated data signalwith the computer-usable program code embodied therewith, either inbaseband or as part of a carrier wave. Program code may be transmittedusing any appropriate wired or wireless medium, including wireline,optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentdisclosure may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork, including a local area network (LAN) or a wide area network(WAN), or the connection may be made to an external computer (forexample, through the Internet using an Internet Service Provider).Cooperative program execution may be for a fee based on a commercialtransaction, such as a negotiated rate (offer/accept) arrangement,established and/or customary rates, and may include micropaymentsbetween device(s) cooperatively executing the program or storing and/ormanaging associated data. The present disclosure is described withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems) and computer program products according toembodiments of the disclosure. It will be understood that each block ofthe flowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, can beimplemented by program instructions. Program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe machine, computer, or other programmable data processing apparatus,to provide for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

These program instructions may also be stored in a machine readablemedium that can direct a machine, computer or other programmable dataprocessing apparatus to function in a particular manner, such that theinstructions stored in the machine readable medium produce an article ofmanufacture to provide a means to implement the function/act specifiedin the flowchart and/or block diagram block or blocks. The programinstructions may also be loaded onto a machine, computer or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the machine, computer or other programmableapparatus to produce a machine implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

Example 1 may be a system including a first detector having a firstlocation and including a first visual input for a first area, a seconddetector having a second location and including a second visual input ofa second area that may at least temporarily include the first detectorat the first location, and an obstacle, the system comprising: a firstlocation device to determine the first location; a second locationdevice to determine the second location; a location comparator to atleast determine the first location is proximate to the second location;a communication service to at least establish communication between thefirst detector and the second detector at least while the first detectoris proximate to the second detector; and a recognition system to detectobstacles in the second area that may be undetectable in the first area,and to provide an identification of the obstacle with the communicationservice.

Example 2 may be example 1, wherein the recognition system is associatedwith the second detector, and an identification of the obstacle isprovided to the first detector from the second detector.

Example 3 may be example 2, wherein the obstacle is undetectable in thefirst visual input.

Example 4 may be any of examples 1-3, wherein the communication serviceis associated with the first detector and to contact a secondcommunication service associated with the second detector while thedetectors are proximate.

Example 5 may be any of examples 1-4, wherein the communication serviceis associated with the second detector and to initiate communicate withthe first detector while the detectors are proximate.

Example 6 may be any of examples 1-5, further comprising: anauthentication agent associated with the communication service toauthenticate proximity of the first detector to the second detector;wherein the authentication agent is associated with selected ones of thefirst detector, the second detector, or a third-party authenticationservice.

Example 7 may be a method for determining whether to adjust movement ofa first device with respect to an obstacle based in part on datareceived from a second device, the first device having a first locationand a first input data corresponding to a dynamic area associated withthe first device, and the second device having a second location and asecond input data corresponding to a second area proximate to the seconddevice, the method comprising: determining a proximity of the firstdevice and the second device; negotiating a communication sessionbetween the first device and the second device; identifying the obstacleis in the second area but not in the dynamic area; exchanging betweenthe first and the second device, during the proximity, data identifyingthe obstacle; determining whether to adjust movement of the first devicebased at least in part on the data identifying the obstacle.

Example 8 may be example 7, further comprising the first devicereceiving the data from the second device, and performing thedetermining whether to adjust movement based at least in part on thedata.

Example 9 may be any of examples 7-8, further comprising the seconddevice performing at least in part the determining whether to adjustmovement of the first device, and communicating an adjustmentrecommendation to the first device.

Example 10 may be any of examples 7-9, wherein the first device is amobile device, and the second device is a fixed-position device.

Example 11 may be example 10, wherein: the dynamic area represents afirst viewpoint for the first device different from a second viewpointfor the second device; and the obstruction is at least temporarilydetectable from the second viewpoint and undetectable from the firstviewpoint.

Example 12 may be example 11, wherein the first input data correspondsto a first visual input, and the second input data corresponds to asecond visual input.

Example 13 may be any of examples 7-12, further comprising: determiningthe first device has a potential collision with the obstacle;associating the potential collision with the data identifying theobstacle.

Example 14 may be any of examples 7-13, in which the determining theproximity comprises recognizing an identifying characteristic of thefirst device being within the second area.

Example 15 may be examples 14, wherein the second device has anassociated recognition system, and the identifying characteristic is oneor more of: a physical marker on the first device, or, a short-rangewirelessly-detectable identifier.

Example 16 may be any of examples 7-15, further comprising: anauthentication agent to encrypt the communication session with a keyvalid during at least a portion of the proximity of the first device andthe second device; wherein the authentication agent is associated withselected ones of the first detector, the second detector, or athird-party authentication service.

Example 17 may be any of examples 7-16, wherein the first device:negotiates the communication session after the proximity with the seconddevice; identifies the obstacle is in the second area but not in thedynamic area based at least in part on the data identifying theobstacle; and adjusts movement to avoid the obstacle.

Example 18 may be one or more non-transitory computer-readable mediaassociated with an environment including a first detector having a firstlocation and including a first visual input for a first area, a seconddetector having a second location and including a second visual input ofa second area that may at least temporarily include the first detectorat the first location, and an obstacle, the media having instructions toprovide for: a first location device to determine the first location; asecond location device to determine the second location; a locationcomparator to at least determine the first location is proximate to thesecond location; a communication service to at least establishcommunication between the first detector and the second detector atleast while the first detector is proximate to the second detector; anda recognition system to detect obstacles in the second area that may beundetectable in the first area, and to provide an identification of theobstacle with the communication service.

Example 19 may be example 18, in which the recognition system isassociated with the second detector, and the media further comprisinginstructions to perform an identification of the obstacle to be providedto the first detector from the second detector.

Example 20 may be one or more machine accessible media havinginstructions to provide for determining whether to adjust movement of afirst device with respect to an obstacle based in part on data receivedfrom a second device, the first device having a first location and afirst input data corresponding to a dynamic area associated with thefirst device, and the second device having a second location and asecond input data corresponding to a second area proximate to the seconddevice, the instructions, when accessed, result in: determining aproximity of the first device and the second device; negotiating acommunication session between the first device and the second device;identifying the obstacle is in the second area but not in the dynamicarea; exchanging between the first and the second device, during theproximity, data identifying the obstacle; determining whether to adjustmovement of the first device based at least in part on the dataidentifying the obstacle.

Example 21 may be example 20 further comprising instructions to perform:the first device receiving the data from the second device; andperforming the determining whether to adjust movement based at least inpart on the data.

Example 22 may be any of examples 20-21 further comprising instructionsto perform: the second device performing at least in part thedetermining whether to adjust movement of the first device; andcommunicating an adjustment recommendation to the first device.

Example 23 may be any of examples 20-22, further comprising instructionsto perform: determining the first device has a potential collision withthe obstacle;

associating the potential collision with the data identifying theobstacle.

Example 24 may be any of examples 20-23 further comprising instructionsto perform: an authentication agent to encrypt the communication sessionwith a key valid during at least a portion of the proximity of the firstdevice and the second device; wherein the authentication agent isassociated with selected ones of the first detector, the seconddetector, or a third-party authentication service.

Example 25 may be any of examples 20-24 further comprising instructionsfor access by at least the first device, the instructions to perform:negotiating the communication session after the proximity with thesecond device; identify the obstacle is in the second area but not inthe dynamic area based at least in part on the data identifying theobstacle; and adjust movement to avoid the obstacle.

Example 26 may be means for performing any of examples 1-25.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the disclosed embodiments ofthe disclosed device and associated methods without departing from thespirit or scope of the disclosure. Thus, it is intended that the presentdisclosure covers the modifications and variations of the embodimentsdisclosed above provided that the modifications and variations comewithin the scope of any claims and their equivalents.

What is claimed is:
 1. A mobile device, comprising: sensor circuitrydisposed on or in the mobile device, wherein the sensor circuitry is tomonitor a first area; communication circuitry to establish communicationbetween the mobile device and a group of external sensors at least whilethe mobile device is proximate to at least one external sensor in thegroup of external sensors; and processor circuitry connected to thesensor circuitry, wherein the processor circuitry is to: cause thecommunication circuitry to establish the communication between themobile device and the group of external sensors when the mobile deviceis determined to be proximate to the at least one external sensor,receive, from individual external sensors in the group of externalsensors via the communication circuitry, information about a second areathat at least temporarily includes the mobile device and encompasses atleast a portion of the first area, detect an object in the second areathat may be undetectable in the first area based on the receivedinformation, and provide an identification of the detected object to thegroup of external sensors.
 2. The mobile device of claim 1, wherein thereceived information includes information about the detected object, andthe processor circuitry is to: generate a first instance of a model ofthe first area based on sensor data generated by the sensor circuitry;and generate a second instance of the model incorporating the detectedobject into the first instance of the model based on the informationabout the detected object.
 3. The mobile device of claim 2, wherein theprocessor circuitry is to: control one or more components of the mobiledevice based on the second instance of the model.
 4. The mobile deviceof claim 2, wherein the information about the detected object includes atimestamp, an object type of the detected object, a size of the detectedobject, a position of the detected object, and speed information relatedto the detected object.
 5. The mobile device of claim 1, wherein thecommunication circuitry is to establish a direct communication with theexternal sensor using a short-range radio access technology; or thecommunication circuitry is to establish a communication session with theexternal sensor through a mobile communication network.
 6. The mobiledevice of claim 1, wherein the processor circuitry is to: authenticateproximity of the mobile device to the at least one external sensor,wherein the authentication is based on detection of the first mobiledevice by the at least one external sensor.
 7. A method for determiningwhether to adjust movement of a mobile device with respect to anobstacle, the method comprising: monitoring, by the mobile device, afirst area using sensor circuitry disposed on or in the mobile device;negotiating, by the mobile device, a communication session between themobile device and a group of external sensors when the mobile device isdetermined to be proximate to at least one external sensor in the groupof external sensors; receiving, by the mobile device from individualexternal sensors in the group of external sensors during thecommunication session, information about a second area that at leasttemporarily includes the mobile device and encompasses at least aportion of the first area; identifying, by the mobile device, an objectin the second area that may be undetectable in the first area based onthe received information; exchanging data identifying the object betweenthe mobile device and the group of external sensors during thecommunication session; and determining, by the mobile device, whether toadjust movement of the mobile device based at least in part on the dataidentifying the object.
 8. The method of claim 7, further comprising:receiving, by the mobile device, the data from the at least one externalsensor; and performing the determining whether to adjust movement basedat least in part on the data.
 9. The method of claim 7, furthercomprising: receiving, by the mobile device from the at least oneexternal sensor, an adjustment recommendation for adjusting the movementof the mobile device.
 10. The method of claim 7, wherein the mobiledevice is a smartphone, a tablet, a wearable device, or an autonomousvehicle, and the at least one external sensor is a fixed-positiondevice.
 11. The method of claim 10, wherein: the first area represents afirst viewpoint for the mobile device different from a second viewpointfor the at least one external sensor; and the object is at leasttemporarily detectable from the second viewpoint and undetectable fromthe first viewpoint.
 12. The method of claim 7, further comprising:determining, by the mobile device, that the mobile device has apotential collision with the object; and associating, by the mobiledevice, the potential collision with the data identifying the object.13. The method of claim 7, wherein the mobile device is determined to beproximate to the at least one external sensor based on recognition of acharacteristic of the mobile device being within the second area. 14.The method of claim 13, wherein the characteristic is one or more of: aphysical marker on the mobile device or a short-rangewirelessly-detectable identifier.
 15. The method of claim 7, furthercomprising: encrypting the communication session with a key that isvalid while the mobile device and the at least one external sensor areproximate to one another.
 16. The method of claim 7, further comprising:negotiating, by the mobile device, the communication session after themobile device is proximate with the at least one external sensor;identifying, by the mobile device, the object in the second area but notin the first area based at least in part on the data identifying theobject; and adjusting the movement to avoid the object.
 17. One or morenon-transitory computer-readable media comprising instructions tooperate an external sensor in a group of external sensors, whereinexecution of the instructions by one or more processors is to cause theexternal sensor to: monitor a portion of a second area that at leasttemporarily includes a mobile device and encompasses at least a portionof a first area monitored by the mobile device; establish communicationwith the mobile device on behalf of the group of external sensors atleast while the mobile device is proximate to the external sensor; sendinformation about the monitored portion of the second area to the mobiledevice for detection of an object in the second area that may beundetectable in the first area; and receive an identification of thedetected object from the mobile device based on the sent information.18. The media of claim 17, wherein execution of the instructions is tocause the external sensor to: determine an adjustment recommendation foradjusting movement of the mobile device based on the detected object;and send the adjustment recommendation to the mobile device.
 19. One ormore non-transitory machine accessible media comprising instructions,wherein execution of the instructions by a mobile device is to cause themobile device to: monitor a first area using sensor circuitry disposedon or in the mobile device; negotiating a communication session betweenthe mobile device and a group of external sensors when the mobile deviceis determined to be proximate to at least one external sensor in thegroup of external sensors; receive, from individual external sensors inthe group of external sensors during the communication session,information about a second area that at least temporarily includes themobile device and encompasses at least a portion of the first area;detect an object in the second area that may be undetectable in thefirst area based on the received information; exchange data identifyingthe object between the mobile device and the at least one externalsensor, during the communication session; and determine whether toadjust movement of the mobile device based at least in part on the dataidentifying the object.
 20. The media of claim 19, wherein execution ofthe instructions is to cause the mobile device to: receive the data fromthe at least one external sensor; and determine whether to adjustmovement based at least in part on the received data.
 21. The media ofclaim 19, wherein execution of the instructions is to cause the mobiledevice to: receive, from the at least one external sensor, an adjustmentrecommendation for the adjustment of the movement.
 22. The media ofclaim 19, wherein execution of the instructions is to cause the mobiledevice to: determine a potential collision with the object; andassociate the potential collision with the data identifying the object.23. The media of claim 19, wherein execution of the instructions is tocause the mobile device to: encrypt the communication session with a keyvalid during at least a portion of a time while the mobile device isproximate to the at least one external sensor.
 24. The media of claim19, wherein execution of the instructions is to cause the mobile deviceto: negotiate the communication session after the mobile device isproximate to the at least one external sensor; identify the object is inthe second area but not in the first area based at least in part on thedata identifying the object; and cause the movement adjustment to avoidthe object.